Fix RTD versioning with a deep git clone #2913
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Seemed to work fantastically, at least in the prerelease build. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing published Locust version in RTD Docs
Currently the published docs using RTD have the wrong version of Locust during the docs build, because the full Git history isn't there. The
toxtests previously had this issue when the base checkout didn't pull the whole git history. This results in something like the below:This PR updates this based on guidance from RTD's own docs, though it's difficult to actually test that this works without overwriting the current docs 🤔
RTD docs on this here:
https://docs.readthedocs.io/en/stable/build-customization.html#unshallow-git-clone